Skip to content

chore(deps): bump @openclaw/google-meet from 2026.10.9 to 2026.11.2 in /plugins/google-meet - #807

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/google-meet/openclaw/google-meet-2026.11.2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/google-meet/openclaw/google-meet-2026.11.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026

Copy link
Copy Markdown
Contributor

Bumps @openclaw/google-meet from 2026.10.9 to 2026.11.2.

Release notes

Sourced from @​openclaw/google-meet's releases.

openclaw 2026.11.2

OpenClaw v2026.11.2

166 commits · 113 pull requests · 64 contributors

Changes included in this release

The release notes and changelog contain the same content, presented in two formats:

Thanks

@​1052326311 @​651juan @​abacha @​amittell @​anmol0b @​beebee @​cestercian @​DasX @​davidcittadini @​DonnieFi @​eliavb43 @​etzelm @​fhgffy @​Finn763 @​fuller-stack-dev @​g62nkcx4q7-wq @​galiniliev @​hannesrudolph @​holgergruenhagen @​HootRock @​huyengiang101086-spec @​IWhatsskill @​javiermv @​joeykrug @​joshavant @​Kimiyu-186 @​LachieFREEDOM @​LeizhenZhang @​Leon-SK668 @​LiuwqGit @​Marvinthebored @​masatohoshino @​mnowrot @​Nickfost @​nxmxbbd @​obviyus @​Oldrich333 @​OliPlus @​Patrick-Erichsen @​Peetiegonzalez @​pgondhi987 @​potoior @​RomneyDa @​Satoshi-Kusumoto @​SebTardif @​sem00-ft @​shakkernerd @​Solvely-Colin @​steipete @​sukhdeepjohar @​sunlit-deng @​SunnyShu0925 @​TameTheGame @​theimmortal68 @​ullrichg13 @​VACInc @​vincentkoc @​wangmiao0668000666 @​wr-web @​YangManBOBO @​yetval @​Yolo521-bot @​yousan @​zhangguiping-xydt

Release verification

openclaw 2026.11.1

2026.11.1

Highlights

Changes

... (truncated)

Changelog

Sourced from @​openclaw/google-meet's changelog.

Changelog

Release notes: https://docs.openclaw.ai/releases

Each release has its complete changelog below. Audited contribution records are retained separately when available.

... (truncated)

Commits
  • b556fdf test: keep archive lifecycle fixtures out of age maintenance
  • aa20474 test: wait for explicit native catalog discovery readiness
  • f46f008 test(macos): synchronize stalled navigation and report stop state
  • 31efa7a test: keep simulated Darwin listeners outside Linux client ports
  • b4c7fe5 test: clean up late durability dispatches after RPC failure
  • 1a6914c test: distinguish CLI completion reply from early child mention
  • 46bcb1c test: pass voice fallback agent runtime in correct slot
  • 62e4cc1 test: establish legacy exec dispatch before timeout
  • 9cfe377 test: use explicit boolean coercion in durability diagnostics
  • 5534c90 test: format durability phase diagnostics
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@openclaw/google-meet](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.2.
- [Release notes](https://github.com/openclaw/openclaw/releases)
- [Changelog](https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md)
- [Commits](openclaw/openclaw@v2026.10.9...v2026.11.2)

---
updated-dependencies:
- dependency-name: "@openclaw/google-meet"
  dependency-version: 2026.11.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 11, 2026
@clawsweeper

clawsweeper Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Nov 11, 2026
@clawsweeper

clawsweeper Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge.

What this changes

This PR updates the Google Meet fixture fallback package and lockfile from 2026.10.9 to 2026.11.2.

Example: The Google Meet package tag cannot be resolved.

  • Before: Crabpot falls back to @openclaw/google-meet@2026.10.9.
  • After: Crabpot falls back to @openclaw/google-meet@2026.11.2.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) The narrow dependency bump has a definite attribution defect and precedes the recorded host-qualification prerequisite.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot PR is outside the ordinary contributor proof gate; supplied checks do not demonstrate the exact fallback through native host admission.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: No · Fix scope: Complete
User problem: Crabpot's pinned Google Meet fallback trails the newer published plugin release.
Reason: The recorded maintainer direction requires qualifying and promoting an eligible host before reconsidering these fallback updates; this PR advances the package without completing that prerequisite.

Merge readiness

⛔ Blocked before merge - 4 items remain

Keep open: main retains 2026.10.9, so the permitted close condition is unmet; this PR also introduces incorrect source attribution and remains blocked by the recorded host-qualification prerequisite.

Priority: P2
Reviewed head: e47ab1ed801972645005ee9e1b1fed1cd9c4860d

Before merge

  • Update both source references with the fallback version (P2) - When tag resolution falls back to 2026.11.2, neither its registry metadata nor its package supplies gitHead. readPackagePayloadSourceRef then matches the payload against this changed shim version and uses crabpot.config.json's retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, documented as prepared source for 2026.10.9. Reports consequently link the changed artifact to the wrong source revision. Verify the prepared source through publication qualification and update both the manifest reference and this shim's sourceRef together.
  • Resolve merge risk - Before merge, maintainers must complete the eligible-host qualification and promotion tracked in Qualify a newer Default Track host before refreshing official plugin fallbacks #780: the current 2026.10.6 host cannot natively admit this package's >=2026.11.2 plugin API requirement.
  • Product: not worth merging - The recorded maintainer direction requires qualifying and promoting an eligible host before reconsidering these fallback updates; this PR advances the package without completing that prerequisite.
  • Explain or restore the original intent of Fallback artifact and source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 qualified the 2026.10.9 package with matching prepared-source references while preserving host and track selections.

Findings

  • [P2] Update both source references with the fallback version — plugins/google-meet/package.json:7

Provenance

Tests

  • Missing end-to-end proof: Moving-track CI does not establish native admission and execution of the exact 2026.11.2 fallback on a qualified eligible host.
Agent review details

How this fits together

Crabpot resolves configured plugin packages, materializes fallback artifacts when needed, and inspects their contracts to produce compatibility reports and upstream source links.

flowchart TD
  A[Fixture configuration] --> B[Package tag resolution]
  B --> C[Published package]
  B --> D[Pinned fallback shim]
  D --> C
  C --> E[Compatibility inspection]
  E --> F[Reports and source links]
Loading

Technical review

Best possible solution:

Retain the reviewed fallback until the recorded host prerequisite is complete, then qualify 2026.11.2 with publication-derived source references and refreshed report expectations.

Do we have a high-confidence way to reproduce the issue?

Source and archive metadata establish that a materialized 2026.11.2 fallback without gitHead receives the retained 2026.10.9 source reference; no target code or tests were executed.

Is this the best way to solve the issue?

The package-and-lock update uses the existing owner, but it is incomplete without matching source references and premature under the recorded host-qualification decision.

Full review comments:

  • [P2] Update both source references with the fallback version — plugins/google-meet/package.json:7
    When tag resolution falls back to 2026.11.2, neither its registry metadata nor its package supplies gitHead. readPackagePayloadSourceRef then matches the payload against this changed shim version and uses crabpot.config.json's retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, documented as prepared source for 2026.10.9. Reports consequently link the changed artifact to the wrong source revision. Verify the prepared source through publication qualification and update both the manifest reference and this shim's sourceRef together.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 90b39250dd03.

Merge-risk options

Maintainer options:

  1. Hold for host qualification (recommended)
    Maintainers retain the current fallback until the existing host qualification and promotion prerequisite is complete.
  2. Complete the prerequisite before landing
    Maintainers qualify and promote an eligible host in a separate focused change, then qualify the exact package and source pair.

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

Likely related people:

  • Peter Steinberger: Raw commit aa34909 adds plugins/google-meet/package.json:15 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: aa349094d146; files: plugins/google-meet/package.json)
  • Vincent Koc: Raw commit 614b320 adds plugins/google-meet/package.json:5 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 614b3209ea42; files: plugins/google-meet/package.json)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P2: This affects fixture provenance and qualification, with no demonstrated urgent deployed-user outage.
  • add merge-risk: 🚨 compatibility: The fallback raises its plugin API floor to >=2026.11.2 while the qualified host remains 2026.10.6; the recorded prerequisite has not been completed.
  • add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool and patch quality is 🦪 silver shellfish.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Label justifications:

  • P2: This affects fixture provenance and qualification, with no demonstrated urgent deployed-user outage.
  • merge-risk: 🚨 compatibility: The fallback raises its plugin API floor to >=2026.11.2 while the qualified host remains 2026.10.6; the recorded prerequisite has not been completed.
  • rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool and patch quality is 🦪 silver shellfish.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 11, 2026, 4:39 AM ET / 09:39 UTC.

@steipete

Copy link
Copy Markdown
Contributor

Closing this unqualified fallback update pending #780. The exact registry manifest requires plugin API >=2026.11.2, while Crabpot’s qualified Default Track host remains 2026.10.6. Native host admission skips this incompatible package; a green report against a moving artifact does not qualify this fallback. After the separately owned host qualification/promotion, the cohort can be refreshed together with verified publication-source references. The current fallback and source pins are retained.

@steipete steipete closed this Nov 14, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/google-meet/openclaw/google-meet-2026.11.2 branch November 14, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. P2 Normal priority bug or improvement with limited blast radius. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant